For this analysis, General Transit Feed Specification (GTFS) were obtained from the STOPS model the represent transit service in both the build and no-build scenarios. GTFS files contain specifications describing service characteristics. The following maps and tables represent the differences between the build and no-build GTFS feeds used in this analysis. This difference represents all of the change in accessibility measured between the two scenarios, as no other parameters were changed in calculating the build and no-build accessibility results. GTFS files for this analysis were obtained directly from the STOPS “STOPS_GTFOutput” folder. Further information on STOPS GTFS in the STOPS model can be found in the (STOPS User Guide)[https://www.transit.dot.gov/sites/fta.dot.gov/files/docs/STOPS_1.50_user_documentation_v5.pdf].
The following maps illustrate the transit network in the general study area as represented in build and no-build scenarios. The network datasets plotted below were built directly from the GTFS feeds, and provide a spatial perspective of the data.
Differences in the following core GTFS tables are documented: Stops.txt, Trips.txt, Stop_times.txt, and Frequencies.txt.
The trips file represents a single route with a seven-day travel profile. The file further splits the route into trips, each identified by a specific ID, that reflect the various frequencies of the line.
The stop times file represents the schedule of transit service, and can be analyzed to identify transit vehicle schedules and run times between station pairs.
The stops file contains the location of all transit stops in the network.